Skip to content

chore: explain status and proceedings of the DSP#255

Open
ssteinbuss wants to merge 1 commit intomainfrom
chore--explain-status-and-proceedings-of-the-DSP
Open

chore: explain status and proceedings of the DSP#255
ssteinbuss wants to merge 1 commit intomainfrom
chore--explain-status-and-proceedings-of-the-DSP

Conversation

@ssteinbuss
Copy link
Contributor

What this PR changes/adds

Add some status and next steps information on the standardization path

Why it does that

Stakeholder considerations

Linked Issue(s)

Closes #254

Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Copy link
Contributor

@arnoweiss arnoweiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-I'd prefer to see this info in the top-level README.md but wouldn't block merging it to a new file like suggested. If that's decided, it should be properly linked in the top-level README.md.

## Current Status
- The specification and supporting materials are in active development within this repository.
- The [release 2025-1](https://github.com/eclipse-dataspace-protocol-base/DataspaceProtocol/releases/tag/2025-1-err1) has been approved by the Eclipse Foundation and the Eclipse Dataspace Working Group.
- This release has been sent as PAS Submission to the ISO/IEC secretariat. An editorial review is conducted before the DIS ballot starts. (See the details of the procedure [here]() )
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link is missing.

- This release has been sent as PAS Submission to the ISO/IEC secretariat. An editorial review is conducted before the DIS ballot starts. (See the details of the procedure [here]() )
- The Eclipse Dataspace Protocol team follows the common practice in ISO/IEC standardization to not work on documents while they are under ballot (stand-still).

## Procedure to Be Followed
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would move this section up, following the justification, and keep it abstract. Meaning: no check marks and add three steps/subprocesses before current step 1: GitHub release, Eclipse Foundation Release (incl. EDWG approval), submission to ISO. It must be clear that this process is to be followed for every "official modification" of the spec.

4. Submit the PAS package to ISO/IEC JTC via the Eclipse Foundation. (Done :white_check_mark:)
5. Respond to any comments from ISO/IEC review and, if necessary, update the specification for publication.

## Next Steps
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could be merged with "current status" section.

- **Industry alignment:** A PAS submission accelerates recognition of the specification as a stable, industry-ready baseline while allowing the community to retain control over the evolution of the specification.
- **Faster route to adoption:** The PAS route is designed to enable faster publication and uptake than a full international standard, which is important for technologies that require timely adoption.

## Current Status
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add date of status

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore: explain status and proceedings of the DSP

3 participants